Skip Headers

Oracle® Enterprise Manager Grid Control Installation and Basic Configuration 10g Release 2 (10.2.0.1) for Linux x86 Part Number B16228-03 |
Home | Book List | Contents | Index | Master Index | Feedback

Previous | Next
| View PDF

# I Enterprise Manager Java Console

In addition to using Oracle Enterprise Manager Database Control or Grid Control to manage an Oracle Database 10g database, you can also use the Oracle Enterprise Manager Java Console to manage databases from this release or previous releases. The Java Console is installed by the Administrator installation type.

Note: Oracle recommends that you use Grid Control or Database Control rather than the Java Console when possible. All Java Console functionality will be migrated to Grid Control in future releases. The Java Console will no longer be available once functionality migration is complete.

## Running Enterprise Manager Java Console

To start the Java Console, follow these steps:

1. Set the ORACLE_HOME environment variable to specify the Oracle home directory where you installed the Oracle Client.

2. Depending on your platform, set the shared library path environment variable for your system to include the following directories:

3. Enter the following command to start the Java Console:

       $ $ORACLE_HOME/bin/oemapp console

   Or

       $ $ORACLE_HOME/bin/oemapp dbastudio

   Table I-1 Required Environment Variable Setting

   AIX | LIBPATH |
       $ORACLE_HOME/lib32:$ORACLE_HOME/lib:
       $LIBPATH
   HP-UX | SHLIB_PATH |
       $ORACLE_HOME/lib32:$ORACLE_HOME/lib:
       $SHLIB_PATH
   Linux | LD_LIBRARY_PATH |
       $ORACLE_HOME/lib:$LD_LIBRARY_PATH
   Solaris | LD_LIBRARY_PATH |
       $ORACLE_HOME/lib32:$ORACLE_HOME/lib:
       $LD_LIBRARY_PATH
   Tru64 UNIX | LD_LIBRARY_PATH |
       $ORACLE_HOME/lib:$LD_LIBRARY_PATH

## Configuring Change Manager

The Change Manager application is the Oracle Change Management Pack central interface. Change Manager gives you direct or indirect access to all of the Oracle Change Management Pack operations (in cases where Change Manager cannot directly perform an operation, such as capturing or comparing object definitions, Change Manager starts the application that performs that operation). All change management information is stored in the standalone repository.

When connected to the standalone repository:

- Change Manager provides access to the Oracle Change Management Pack objects in the standalone repository. Because the standalone repository contains only objects that you created, the Change Manager navigator tree displays only your Change Management Pack objects.

- You have full access to your objects, but no access to any other objects.

- Other Change Management Pack applications started from Change Manager also run standalone.

- You cannot submit change plan scripts as jobs using the Oracle Enterprise Manager job system, but you can execute scripts interactively.

The first time Change Manager is accessed, you are prompted to create a database user who will own the standalone repository schema, or you are prompted to specify a user name and password if you have already created the user.

Because this database user must have certain roles and privileges, Oracle recommends creating a new database user to own the standalone repository schema. In addition, because certain tablespace attributes are required for the standalone repository, you should also create a new tablespace. Once the user and tablespace have been created, you can supply the user's user name and password, and the standalone application automatically creates the standalone repository for you.

If you do not want to be prompted with the standalone Repository Login dialog every time you start your Change Manager, select the Save password and automatically log into the repository next time option to save the credentials for future use.

### Creating a Standalone Repository

Before creating a standalone repository:

1. Make sure the database used for the repository is supported.

2. Create a tablespace for the standalone repository.

3. Create a database user for the standalone repository.

#### Database Version Requirements for the Standalone Repository

The following database releases are supported for the standalone repository:

- Enterprise Edition or Standard Edition Release 10.1.x

- Enterprise Edition or Standard Edition Release 9.2.x

- Enterprise Edition or Standard Edition Release 9.0.1.x

You must ensure that the database in which the repository will be placed has object support. If it does not, repository creation fails. Either select another database that has object support, or install and enable object support on the chosen database.

Note: Object support is installed and enabled by default for database releases 10.1.x, 9.2.x, 9.0.1.x, and 8.1.7.x.

#### Create a Tablespace for the Standalone Repository

Create a tablespace with the following attributes:

- Type: Permanent

- Storage attributes: for Extent Management, use Locally managed

- Datafile attributes:

  - Size:

    - For 2 Kb blocks: 16 MB

    - For 4 Kb blocks: 24 MB

    - For 8 Kb blocks: 32 MB

    - For sizes above 8 KB: 64 MB

  - Reuse Existing File: Yes

  - AUTOEXTEND: Yes

  - AUTOEXTEND increment: 5MB

  - AUTOEXTEND maximum: 2000MB

To create a tablespace for the standalone repository, first select the database in which you want to place the standalone repository, ensuring it meets the requirements outlined. Then, follow the procedure described in this section:

1. Start the Oracle Enterprise Manager Java Console.

   You can start the standalone console from the command line using the command:

       oemapp console

2. Click the + next to Databases to display the list of databases.

3. Double-click the database node in the Navigator and connect to the database as a user with the NORMAL privileges.

4. Choose Create from the Object menu. The Create Object List dialog appears.

5. Expand the database node in the Create Object List dialog and select Tablespace, then click Create. The Create Tablespace property sheet appears.

6. In the Create Tablespace Property Sheet's General page,

   - Enter the name of the new tablespace, OEM_REPOSITORY.

   - Specify that the tablespace will be used to hold permanent database objects.

7. In the Datafile section, enter the size of the new datafile. The File Name and File Directory columns should already contain default entries. The datafile is called OEM_REPOSITORY.dbf or OEM_REPOSITORY.ora depending on the version of the database.

8. Right-click the + next to OEM_REPOSITORY.dbf and choose Edit. The Create Datafile property sheet appears.

9. In the Create Datafile's General page, select the Reuse Existing File box.

10. In the Create Datafile's Storage page, fill the appropriate attributes:

    1. Select the Automatically extend datafile when full (AUTOEXTEND) option so that the datafile automatically increases in size when more space is needed in the database.

    2. Specify 5 MB as the Increment.

    3. Specify 2000 MB as the Maximum Size.

11. Click OK in the Create Datafile property sheet.

12. In the Create Tablespace Property Sheet's Storage page, select the Locally Managed option as the method of space management.

13. Click Create in the Create Tablespace Property Sheet.

#### Create a Database user for Standalone Repository

A standalone repository is owned by a database user. A database user, in other words, a repository schema user, who will own the repository must be created before the standalone repository can be created by Enterprise Manager.

To create a database user who will own the standalone repository, follow the procedure described below:

1. Start the standalone Console.

2. Double-click the database node in the Navigator and connect to the database as a user with the NORMAL role.

3. Choose Create from the Object menu. The Create Object List dialog appears. Expand the database node in the Create Object List dialog and select User, then click Create. The Create User property sheet appears.

4. In the General page, provide the name of the user and its password, and select OEM_REPOSITORY as the default tablespace and TEMP as the temporary tablespace.

5. In the System Privileges page, grant the CREATE PROCEDURE, CREATE TRIGGER, CREATE TYPE, EXECUTE ANY PROCEDURE, EXECUTE ANY TYPE, SELECT ANY DICTIONARY (for 9i), and SELECT ANY TABLE roles to the repository user.

6. In the Quota page, specify unlimited for OEM_REPOSITORY and TEMP.

7. Click Create in the Create User property sheet.

Once you have a tablespace and a repository user, start a standalone application that requires a standalone repository.

When the dialog appears informing you that certain features of Enterprise Manager require a standalone repository and you must create a new database user to own the standalone repository schema, click OK to close the dialog since you have already created the user.

Supply the user's user name and password for the repository login and click OK. The standalone application automatically creates the standalone repository for you.

## Starting Change Manager

You can start the Change Manager application in any of the following ways:

- From the Oracle Enterprise Manager Java Console, use any of these methods:

  - Select a database in the navigator panel, click the right mouse button, point to the Related Tools menu option, then click Change Manager.

  - On the Tools menu, point to Change Management Pack, then click Change Manager.

  - Click the Change Management Pack drawer, then click the Change Manager icon.

- Set the default to the ORACLE_HOME/bin directory (where ORACLE_HOME is the directory in which Oracle Enterprise Manager is installed), then enter the following in lowercase characters at the command line prompt:

      oemapp ocm